Operator Library: Hardware Platform
This operator generates trigger packets according to signal edges detected at the input port.
There are two possible implementations of the CxpTxTrigger operator that depend on the number of input ports:
-
Single Input Port: The Tx Trigger specification from CXP 1.X standard is used. CXPLinkTrigger0 is sent with every rising edge on the input port I. When the TxTriggerPacketMode parameter is not set to RisingEdgeOnly, CXPLinkTrigger1 is sent with every falling edge on the input port I. If the operator is instantiated with a single input port, the name of said port is I.
-
Multiple Input Ports: The Tx Trigger specification from CXP 2.X standard is used (LSB of delay is used to implement trigger 2 and 3). Every input port is assigned to one of the CXPLinkTriggers from 0 to 3. Every rising edge on an input port will result in the corresponding CXPLinkTrigger packet being sent. For this configuration the TxTriggerPacketMode parameter is deactivated. If the operator is instantiated with multiple input ports, the names of the input ports range from LinkTrigger0 to LinkTrigger3 depending on the number of configured input ports.
The operator uses one resource CxpTxTriggerPort, which is in range {0, 1, 2, 3} for imaFlex CXP-12 Quad, and in range {0, 1, 2, 3, 4} for imaFlex CXP-12 Penta. This resource corresponds to the CXP channel in which the trigger packets are sent.
Since a rising edge (and potentially falling edge for single input ports) on the input ports leads to a full trigger packet being sent, there must be a gap between edges. If the gap between edges is not large enough it leads to 'over-triggering'. This means only the first edge results in a trigger packet, while the suceeding edges are ignored. The CxpPortStatus operator contains the parameter TxTriggerOverRequestCount, which counts the number of times that over-triggering has occurred. If multiple trigger edges are lost in a very short period of time due to over-triggering (e.g. trigger edges on parallel input ports), the TxTriggerOverRequestCount might not count the exact number of lost trigger edges. Instead, the multiple over-triggers will lead to a single increment of TxTriggerOverRequestCount.
| Available for Hardware Platform |
|---|
| imaFlex CXP-12 Penta |
| imaFlex CXP-12 Quad |
| Property | Value |
|---|---|
| Operator Type | M |
| Input Links | I, n == 1, trigger input LinkTrigger[n], n > 1, trigger input |
| Link Parameter | Input Link I, n == 1 | Input Link LinkTrigger[n], n > 1 |
|---|---|---|
| Bit Width | 1 | 1 |
| Arithmetic | unsigned | unsigned |
| Parallelism | 1 | 1 |
| Kernel Columns | 1 | 1 |
| Kernel Rows | 1 | 1 |
| Img Protocol | VALT_SIGNAL | VALT_SIGNAL |
| Color Format | VAF_GRAY | VAF_GRAY |
| Color Flavor | FL_NONE | FL_NONE |
| Max. Img Width | any | any |
| Max. Img Height | any | any |
| TxTriggerPacketMode | |
|---|---|
| Type | Dynamic Write parameter |
| Default | RisingFallingEdge |
| Range | {RisingFallingEdge,RisingEdgeOnly} |
|
This parameter defines for which trigger input edge a trigger packet is sent. If you select the RisingFallingEdge mode, a packet is sent for rising and falling edges. If you select the RisingEdgeOnly mode, only packets are sent for the rising edge. This parameter is only active, when only a single input port is used. |
|
The use of operator CxpTxTrigger is shown in the following examples:
-
'Area Scan Trigger for imaFlex CXP-12 Quad'
An area scan trigger for CoaXPress12 is presented. External sources, an internal frequency generator or software trigger pulses can be used for trigger generation.
Prev
